fix(compute): register the dummy pool driver under its own kind - #539
Merged
Conversation
The gcn_machine_pool_driver entry point was registered as "DummyPoolDriver" instead of "dummy", so it never matched DummyPoolDriverSpec.KIND and could never be loaded - unlike its "libvirt" sibling entry, which correctly used the driver spec's KIND as the entry point name.
slashburygin
approved these changes
Jul 29, 2026
gmelikov
approved these changes
Jul 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The gcn_machine_pool_driver entry point was registered as "DummyPoolDriver" instead of "dummy", so it never matched DummyPoolDriverSpec.KIND and could never be loaded - unlike its "libvirt" sibling entry, which correctly used the driver spec's KIND as the entry point name.